home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: Button part
- Sent: 7/3/96 10:12 AM
- Received: 7/3/96 10:21 AM
- From: Troy Gaul, tgaul@apple.com
- Reply-To: ODF Interest, ODF-Interest@CILabs.ORG
- To: OpenDoc Development Framework Discussion List, ODF-Interest@CILabs.
-
- >After converting our part to R1, we no longer can embed the CyberButton
- >part. When attempting to do so, we get a fatal error inside the
- >CyberButton part. Is there an incompatability between the new ODF R1 and
- >Cyberdog? If so, is there a fix? (We are using Cyperdog release 1.0)
- >Being able to embed this part is a key to our product.
-
- This problem in particular comes from the fact that ODF 1 doesn't handle
- AcquireContainingPartProperties correctly.
-
- The problem is that FW_CODPart::AcquireContainingPartProperties (in
- FWODPart.cpp) assumes incorrectly that the frame passed into the routine
- is one of its display frames. In fact, that frame is an embedded frame
- belonging to another part. Getting the FW_CFrame from that frame will
- fail (but, since the part info is not NULL, it will try to dispatch to it
- as if it were a CFrame).
-
- There are a couple ways you could fix this (depending on whether you want
- to support any containing part properties or not). I understand ODF 2
- has some changes in this regard, so if you want to support them, you
- might want to use the same design to ease migration.
-
- _troy
-
- ......................................................................
- Troy Gaul tgaul@apple.com
- Apple Computer, Inc. OpenDoc Partsmith
-
-
-